SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 46183: java.lang.NullPointerException at com.sas.solutions.di.studio.mdo.controls.PlanFacts.refresh(PlanFacts.java:388)

DetailsAboutRate It

When viewing Plan Weekly Details in SAS® High-Performance Markdown Optimization, you might encounter an error window containing the following message:

An error occurred in SAS High-Performance Markdown Optimization. Restart or Exit the application.

When you click the Show Details button, you might encounter the following detailed error message:

java.lang.NullPointerException at com.sas.solutions.di.studio.mdo.controls.PlanFacts.refresh(PlanFacts.java:388) at com.sas.solutions.di.studio.mdo.views.vcp.PlanDetailsWeeklyVCP.refresh(PlanDetailsWeeklyVCP.java:975) at com.sas.solutions.di.studio.views.AbstractPagedView.internalShowContentProvider(AbstractPagedView.java:949) at com.sas.solutions.di.studio.views.AbstractPagedView.showContentProvider(AbstractPagedView.java:898) at com.sas.solutions.di.studio.views.AbstractPagedView.showContentProvider(AbstractPagedView.java:887) at com.sas.solutions.di.studio.views.AbstractPagedView.addContentProvider(AbstractPagedView.java:636) at com.sas.solutions.di.studio.mdo.views.MarkdownView.appendOrReplacePlanVCP(MarkdownView.java:703) at com.sas.solutions.di.studio.mdo.views.MarkdownView.launchPlanDetailsWeekly(MarkdownView.java:748) at com.sas.solutions.di.studio.mdo.views.vcp.PlanListVCP.handleLaunchPlanDetailsWeeklyView(PlanListVCP.java:1721) at com.sas.solutions.di.studio.mdo.views.vcp.PlanListVCP$14.widgetSelected(PlanListVCP.java:701) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.sas.solutions.di.studio.runtime.internal.StudioApplication.start(StudioApplication.java:202) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

This error occurs when you try to open the Plan Weekly Details view and the current metrics are all null. Under normal circumstances, you should not encounter entirely null metrics, so you should research what might be causing them.

There is no workaround for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS High-Performance Markdown OptimizationLinux for x644.3_M25.29.2 TS2M39.3 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.